Thanks, you will have to add a DCO signoff to the commit message see https://github.com/containers/podman/blob/main/CONTRIBUTING.md#sign-your-prs

Also if you are going to repush it would be nice to add the Fixes: #26374 also as part of the commit message.

Thanks for your check.
I added the DCO signoff and Fixes: #26374 to the commit message and repush it.

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, shu-kitamura

The full list of commands accepted by this bot can be found here.

The pull request process is described here

@Luap99 May I ask a question?

I have read the code review process. I understand that PRs are merged in the following way:

• In phase 1, the lgtm label is added based on the reviewer's comments
• In phase 2, the approved label is added based on the approver's comments
• In phase 3, it is automatically merged (if the conditions are met)

Currently, the approved label has been added, but the lgtm label has not yet been added.
Do I need to get another reviewer to review this PR?

• In phase 1, the lgtm label is added based on the reviewer's comments
• In phase 2, the approved label is added based on the approver's comments

@Luap99 May I ask a question?

I have read the code review process. I understand that PRs are merged in the following way:

• In phase 1, the lgtm label is added based on the reviewer's comments
• In phase 2, the approved label is added based on the approver's comments
• In phase 3, it is automatically merged (if the conditions are met)

Currently, the approved label has been added, but the lgtm label has not yet been added. Do I need to get another reviewer to review this PR?

Yes, the process requires a second lgtm where the lgtm is preceeded by a /. Also, imho, phase 2 can occur before phase 1 because we don't really take advantage of the approved label. I will review and merge your PR now if it is up to snuff.

/lgtm